Digital asset data type definitions

ABSTRACT

Data definitions for digital assets, such as, for example, audio, video, photographs, graphics, and electronic documents, are provided that allow these different asset types to be stored in a single database. The definitions are preferably in XML and can be used as a standardized dictionary to more efficiently and economically manage digital assets, thus improving system interoperability between companies or organizations within a company. A digital asset ordering interface, hardware system, software arrangement, and application interface configuration advantageously using these data definitions are also provided.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a continuation of co-pending U.S. application Ser. No.11/232,263, filed Sep. 20, 2005, now U.S. Pat. No. ______, which is adivision of U.S. application Ser. No. 10/016,679, filed Dec. 12, 2001,which claims the benefit of U.S. Provisional Application No. 60/254,991,filed Dec. 12, 2000.

BACKGROUND OF THE INVENTION

This invention relates to storing, retrieving, and tracking digitaldata. More particularly, this invention relates to data definitions thatallow disparate types of digital assets, such as, for example,photographs, graphics, audio, video, and text documents, to be easilyand economically stored, retrieved, and tracked.

Data definitions may be written using XML (extensible markup language).XML is a condensed form of SGML (standard generalized markup language),which is an information management standard that provides documents thatretain formatting, indexing, and linked information—independent ofapplication and platform. XML and SGML can be used to organize andpresent information on the World Wide Web.

Many companies maintain or access large libraries of various audio,visual, and textual assets. Such assets typically include content andmetadata. Content may be, for example, still photographs, audiorecordings, video recordings, combined audio/video recordings, combinedaudio/still photograph recordings, graphics, etc. Metadata is“information about information,” that is, information used to identifyor classify the content. Metadata can include, for example, contenttitles, version numbers, authors, captions, and other descriptiveinformation relevant to the content.

Such assets are often stored in disparate repositories and on disparatemedia (e.g. audio and video cassette tapes, motion picture film,photographic negatives, digital video discs, etc.). Accordingly, asignificant amount of time is often required to locate a particularasset and then deliver a copy of it. For example, it may take severaldays to locate and manually copy an audio track stored on a reel-to-reeltape located at a creative services or marketing department of a companyin California and then have that copy shipped to a business affairsdepartment or sister company in New York. This process, known asrepurposing, is manually intensive and prone to errors. Furthermore,keeping track of asset usage (e.g., who has asset copies) is also amanually intensive process prone to errors. Accordingly, it can costthousands or even millions of dollars annually for a company to managesuch assets.

In an attempt to reduce these costs, some companies store assetsdigitally in one or more computer databases. These assets can then beretrieved electronically using appropriate software applications.However, known applications are limited. For example, databases arecommonly structured to store only one type of digital asset, such as,for example, only photographs. The number, size, and formats of recordfields used in the database, characters delimiting the end of files,file size of database records, etc. are all usually customized (andlimited) to that one type of asset. Even those few databases that areknown to store more than one asset type are also limited with respect torecord field definitions and record file size, making them incompatiblefor use with many other types of digital assets. Such databases are thusimpractical for storing a large variety of different types of digitalassets.

In sum, storing disparate asset types in a single repository havinginformation and formatting sufficient for identification and retrievalby a single software application or computer platform is not known.Moreover, no standardized definitional dictionary for digital assets isknown. Thus, system interoperability between two or more companies ortwo or more organizations within a company having different types ofdigital assets is still very difficult.

In view of the foregoing, it would be desirable to be able to provide astandardized dictionary of data definitions for disparate types ofdigital assets.

It would also be desirable to be able to provide data definitions forapplication and platform independent search, retrieval, delivery, andtracking of digital assets.

It would further be desirable to be able to provide data definitionsthat reduce digital asset search time.

It would still further be desirable to be able to provide datadefinitions that reduce digital asset delivery time.

SUMMARY OF THE INVENTION

It is an object of this invention to provide a standardized dictionaryof data definitions for disparate types of digital assets.

It is also an object of this invention to provide data definitions forapplication and platform independent search, retrieval, delivery, andtracking of digital assets.

It is a further object of this invention to provide data definitionsthat reduce digital asset search time.

It is a still further object of this invention to provide datadefinitions that reduce digital asset delivery time.

In accordance with this invention, data definitions are provided fordigital assets that include a hierarchical structure that reflects therelationships between attributes and categories of content. Thesedefinitions, preferably encoded in XML, can be used as a standardizeddictionary to create a digital asset library that is easily andeconomically manageable. The data definitions are applicable to digitalassets of disparate data types and include metadata identifierssufficient to uniquely identify those digital assets.

A method of retrieving digital assets from a digital asset library isalso provided.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects and advantages of the invention will beapparent upon consideration of the following detailed description, takenin conjunction with the accompanying drawings, in which like referencecharacters refer to like parts throughout, and in which:

FIG. 1 is a flow chart of an interface for ordering digital assets usingdata definitions according to the invention;

FIG. 2 is a block diagram of an embodiment of a hardware system withinwhich the invention can be used;

FIG. 3 is a block diagram of an embodiment of integrated softwareaccording to the invention;

FIG. 4 is a block diagram of an embodiment of an application interfaceconfiguration according to the invention;

FIG. 5 shows an embodiment of a display screen for asset searchingaccording to the invention;

FIG. 6 shows an embodiment of a display screen for search resultsaccording to the invention; and

FIG. 7 is a high level block diagram showing an embodiment of a documenttype definition (DTD) for digital assets according to the invention.

DETAILED DESCRIPTION OF THE INVENTION

The invention provides data definitions, preferably in XML, fordisparate types of digital assets, such as, for example, artwork, logos,photographs, video, graphics, music, still photographs, promotionstills, promos (e.g., an audio or video promotional announcement),tapes, soundtracks, text, video frames (a single image from a videorecording), video clips (a group of images from a video recording), anddailies (unedited and unprocessed video or film typically recorded theprevious day). Digital assets include content (i.e., the actual assetdata) and metadata. Data definitions of the invention advantageouslypermit a single database to be used for storing, retrieving, andtracking different types of assets whose contents are preferably storedeither on the same computer as the database, in the database, on acomputer linked to the database via the same network, or combinationsthereof. These data definitions allow, for example, employees,affiliates, and customers to relatively easily and economicallyreplicate or transfer assets between repositories where the assets arelocated and destinations where the assets are currently needed.Furthermore, electronic records can be created to allow usage of thoseassets to be easily tracked. Thus, the costs associated with managingthose assets are significantly reduced.

FIG. 1 shows an interface for searching and ordering digital assetsfacilitated by the invention. System Home Screen 101 is preferably thefirst screen a user views when searching for a digital asset (e.g., avideo program). While at Home Screen 101, users may enter searchcriteria before proceeding to another screen. However, this isalternatively not necessary. From Home Screen 101, the user may proceedin one of the following ways: along path 102 to Login Screen 103, alongpath 104 to Register Screen 105, along path 106 to Advanced SearchScreen 107, along path 108 to Top Picks Screen 109, along path 110 toLatest Releases Screen 111, or along path 112 to Editor's Choice Screen113.

At Login Screen 103, users login to a secured version of a search systemassociated with interface 100. A user entering Login Screen 103 alongpath 102 is preferably directed along path 114 to User Home Screen 115unless the user entered search criteria while viewing Home Screen 101.In that case, the user is preferably directed to Order Confirmation andDownload Screen 117 along path 116. Similarly, if the user entered LoginScreen 103 along path 127, the user is also preferably directed to OrderConfirmation and Download Screen 117.

At Register Screen 105, users register to use the system. Users may beassigned or may freely choose a username, password, and any otherrelevant identifying information. Users may be prompted by RegisterScreen 105 to enter information deemed relevant or necessary by thesystem. After registering, users are preferably directed along path 118to User Home Screen 115.

At Advanced Search Screen 107 users enter or are given pre-definedcriteria with which the database of the invention can be searched.Screen 107 preferably allows users to generate advanced search criteriaincluding, but not limited to, searching specific strings, numericvalues, fields or combinations of fields containing data, as well asallowing users to define complex or simple search expressions usingboolean or other logic, wildcards, multiple search criteria, or anyother type of search functionality. Preferably, upon an indication by auser or upon a pre-defined system event (for example, expiration of atimer), a user will be directed along path 119 to Search Results Screen120.

At Top Picks Screen 109, a user can view and select from a subset ofassets defined in the database. This subset may be predefined by theuser, the system, or a system administrator. The subset may be definedas the most viewed assets, most searched for assets, most retrievedassets, most popular assets, or top assets based on a criteria definedby a user, the system, or an administrator.

At Latest Releases Screen 111, a user can view and select from a subsetof assets in the database. This data is preferably a subset of the mostrecently added assets in the database. However, the subset may bedefined as the most recently released assets, most recently producedassets, or any other desired subset of data in the database.

At Editor's Choice Screen 113, a user can view and select from a subsetof assets defined in the database. This subset is preferably a selectionof assets that one or more editors, within the company or organizationviewing or providing the database, has selected as being desirable forviewing based on one or more criteria defined by the editors.

At User Home Screen 115, a user can view personalized or standardinformation relating to that user's usage of the database. The systemmay present the user with search possibilities, the ability to view somesubset of assets defined in the database, a listing of data that may beuseful in some respect, and any other relevant information or functionalpossibilities. Preferably, upon an indication by a user or upon apre-defined system event (for example, expiration of a timer), the useris directed along path 122 to Content Detail Screen 123.

At Search Results Screen 120, a user can view and select from a subsetof data retrieved in accordance with criteria defined by the user whileviewing Advanced Search Screen 107 and possibly in accordance with oneor more database enforced criteria. Upon indicating a selection of oneor more assets, a user is directed along path 121 to Content DetailScreen 123.

In addition to being directed along path 121 or 122 as described, a usermay be directed along path 124 from any of screens 109, 111, or 113 toContent Detail Screen 123. A user may be automatically directed toscreen 123 if a small number of asset definitions are the only items theuser wishes to view. For instance, if a user performs a complex searchand the system finds only one asset satisfying the search criteria, thesystem may automatically bypass Search Results Screen 120 and displayContent Detail Screen 123.

At Content Detail Screen 123, a user can view all or part of the summarydata directly related to one or more items selected manually orautomatically by the user. Preferably, upon an indication by the user orupon a pre-defined system event (for example, expiration of a timer), auser is directed along path 125 to Order Options Screen 126.

At Order Options Screen 126, a user can view and select from optionsrelated to ordering and downloading data for which summary data wasviewed while viewing Content Detail Screen 123. These options mayinclude billing, routing, formatting, data transmission, delivery date,delivery time, and other relevant options. Upon indication by a user orupon a pre-defined system event, the user is directed along path 127 toLogin Screen 103 or along path 128 to Order Confirmation And DownloadScreen 117. Preferably, a user is directed along path 127 when the userhas not logged in using Login Screen 103. Alternatively, a user isdirected along path 128 when the user had previously logged in via LoginScreen 103. In some systems, logging in is not necessary. In othersystems, a user that has logged in but has not taken any decisive action(for instance, has not made an indication at Order Options Screen 126within a specified amount of time after logging in) is directed alongpath 127.

At Order Confirmation And Download Screen 117 the system preferablydisplays details and summary information relating to an asset that wasordered by a user. The user is preferably presented with the opportunityto download or retrieve the asset. Such retrieval may be performedeither electronically or by using devices (such as printers, taperecorders, compact disc writers, digital video disc writers, or otherrecording or printing equipment) to convert an asset stored in adatabase or in an associated or networked computer memory to a digitalor analog item stored in another manner.

Note that any of paths 102, 104, 106, 108, 110, 112, 114, 116, 118, 119,121, 122, 124, 125, or 128 may be traversed in reverse by users thatwish to step backwards in the search and ordering process. Also,securing the search system is not a necessary function of the invention.Note further that all of interface 100 is not necessary for implementingthe invention; an interface employing even a very small subset ofinterface 100 can benefit from the invention. Moreover, additionalprocess paths and functionality (for instance, paths connecting any ofscreens 109, 111, 113, 115, and 123 directly to Search Results Screen120 to allow a user to view search results from a search performed whileviewing any of those screens) can be added to interface 100.

In sum, the data definitions of the invention enable systems usinginterface 100 or similar interfaces to provide satisfactory interactivesearch and response times to users.

FIG. 2 shows a hardware system 200 that can be used to manage digitaldata defined with data definitions in accordance with the invention.System 200 preferably includes one or more servers 201, a securetransmission line 202, at least one secure recording or printing device203, one or more secure access devices (e.g., laptop 204, computer 205,and workstation 206), at least one firewall 207, one or more non-securetransmission lines 208, one or more non-secure access devices (e.g.,computer 209, workstation 210, and laptop 211), and at least onenon-secure recording or printing device 212.

One or more servers 201 store all or part of one or more databases.Servers 201 may be accessed via secure transmission line 202 by secureaccess devices 204-206 or by firewall 207 which has received appropriateindications from non-secure access devices 209-211 via non-securetransmission line 208. Upon receiving appropriate indications fromdevices 204-206 or firewall 207, servers 201 transmit data to devices204-206, firewall 207, or recording or printing device 203, asappropriate, via secure transmission line 202.

Upon receiving appropriate indications (based on security criteria),firewall 207 transmits data to non-secure access devices 209-211 ornon-secure recording or printing device 212, as appropriate, vianon-secured data transmission line 208.

Secure access devices 204-206 and non-secure access devices 209-211 caninclude laptop computers, desktop computers, and workstations (asshown), as well as other types of terminals, wireless devices, personaldigital assistants (PDAs), television set-top boxes, other databases,and other digital devices that can receive user indications and cancommunicate with servers or firewalls.

Severs 201 can be, for example, Sun® servers using the Solaris®platform, Oracle® database servers, or any other appropriate serverplatform. Transmission lines 202 and 208 may use T-1, T-2, or any otherappropriate transmission standards. Alternatively, the invention can bepracticed with a configuration as simple as a single computer that cando the following: store and query a database in its RAM, ROM, hard diskdrive, compact disc, floppy disk, or other suitable storage medium;display visual or play audio content; and receive user indications.

FIG. 3 shows an embodiment of integrated software according to theinvention. Computer 301 (which may be any of secure access devices204-206, firewall 207, and non-secure access devices 209-211)communicates with servers 201. Project applications 303, which arepreferably encoded in XML, transmit a demand 304 for databaseinformation to database 305. Database 305 may be, for example, Oracle®,Sybase®, Microsoft Access®, or any other relational or non-relationaldatabase package. Database 305 creates preferably XML files 306. Anexample of an XML file 306 is shown in Example 2 below. XML files 306are transmitted in HTML format 307 a for viewing graphics with a browser308. Microsoft Internet Explorer® and Netscape Navigator® are twoexamples of browsers that may be used. Preferably, format 307 a is HTMLwith cascading style sheets (CSS).

Alternatively, XML files 306 may be transmitted in XML format 307 b foruse by other applications 309, such as, for example, C, C++, or Javaapplications that may be for a stand-alone screen, front-end GUI, or Webpresentation package. Alternative format 307 b may include XML with CSSfor further processing by applications such as search engines or bots ormay include regular HTML if a still or active display is the only outputrequirement. Bots are programs that typically perform repetitive or timeconsuming tasks on a network (e.g., searching Web sites on theInternet). Examples of formats 307 a and 307 b are shown below inExamples 3a-c.

FIG. 4 shows an embodiment of an application interface configuration inaccordance with the invention. In this configuration, a user providessearch parameters 401 to client application 402, which is active oncomputer 301. Client application 402 converts search parameters 401 intoa demand 304 for database information. Demand 304 may take the form ofan SQL (structured query language) query when database 305 is anSQL-based relational database. Preferably, however, server 201 processesdemand 304 in a server application 404. Server application 404preferably includes the following modules: an XML parser 414, an XSLprocessor 424, and an XML-SQL utility 434. XSL (extensible style sheetlanguage) is a language for specifying style sheets that applyformatting to complex XML data for presentation in HTML and otherformats. XSL can map a single XML element to more than one type ofdisplay object (e.g., both an element in a list and an item in a table).A style sheet is a text file containing code to apply semantics such aspage layout specifications to an HTML document.

After converting demand 304 to SQL format (if necessary depending on thedatabase), application 404 sends query 405 to database 305. Database 305processes query 405 and returns search results 406 to application 404.Application 404 then processes results 406 to create one or more XMLfiles. These XML files are sent by application 404 as data 407 to XSLstyle sheet 408. XSL style sheet 408 processes data 407 and returns aresponse 307 in format 307 a or 307 b, as appropriate. Clientapplication 402 then converts response 307 into a format that can beheard or viewed by the user.

FIG. 5 shows an example of a display that can be used as Advanced SearchScreen 107. Illustrative display 501 includes interactive features 502,503, 504, and 505. Display 501 may alternatively include more or lessinteractive features as appropriate for a given implementation of theinvention. Interactive feature 502, entitled “PLEASE ENTER KEYWORDS TOSEARCH,” accepts user entries of keywords or phrases to be used by XMLproject applications 303 when forming demand 304. For example, “Oscarbelt” may be entered via interactive feature 502 by a user searching fora picture that has metadata containing the description, “Oscar Delahoyawearing a championship belt.” Interactive feature 503, entitled “PLEASESELECT ASSET CATEGORY,” accepts user entries for the type of asset toretrieve. For example, possible asset types are photos, audio, video,text, any combination of these, or any other appropriate asset type.Interactive feature 504, entitled “SEARCH,” allows users to submit asearch request (i.e., have application 303 form a demand 304).Interactive features 505, entitled “DTD,” “XML,” “XSL,” and “XSL SS,”allow a user to select a source code format in which to view datainstead of viewing a composed video screen or hearing a composed audiooutput.

FIG. 6 shows an example of a display that can be used as Search ResultsScreen 120. In this example, illustrative display 601 indicates at 602that 4 photo assets, 1 video asset, and 1 audio asset had been found,and shows at 603 a list of photographic assets, that met the criteria ofa demand 304. Illustrative display 601 preferably includes features 604,605, 606, and 607. Alternatively, display 601 can include more or lessfeatures as desired for a given implementation of the invention.Features 604 interactively accepts user indications of selection orrejection of assets from the displayed list of assets. Features 605 maybe interactive (e.g., a button) or static (e.g., just a display). Inthis example, feature 605 displays an image of the assets associatedwith the retrieved list items. If feature 605 is interactive, it canaccept a user's selection of an asset to be ordered. Feature 606displays descriptive information associated with the assets that met thecriteria of demand 304. Feature 606, like feature 605, may beinteractive to accept user selections of an asset. Feature 607, entitled“ORDER CHECKED,” is interactive and accepts indications that a user hasfinished selecting assets and is ready to proceed along path 121 toContent Detail Screen 123.

FIG. 7 shows an embodiment of a document type definition (DTD) inaccordance with the invention. A DTD is a separate file or document thatcontains formal definitions of all the data elements in a particulartype of XML (or HTML or SGML) document, such as a report or a book. Byconsulting the DTD for a document, a program called a parser (e.g., XMLparser 414) can work with the markup codes that the document contains.DTD 700 includes asset element 701, which defines the type of data to bestored for each digital asset. DTD 700 may also include one or moreother data elements 702 for other uses. For example, asset element 701can contain a core set of definitions, while data element 702 cancontain additional definitions that augment the core set in cases wheresuch additional definitions are required by a particular user.

Asset element 701 preferably includes asset metadata 703, asset typedata 704, and asset content 705. Asset element 701 may also includeadditional definitional information as desired. Asset metadata 703preferably includes the following definitional elements: productidentifier (ID) (e.g., a video program name), version ID, inventory ID,and ownership rights ID. Asset metadata 703 can also include any subsetof these identifiers or any additional identification information.

Asset type data 704 advantageously can include any number ofdefinitional elements relevant to a particular type of asset. Table 1 isa preferred embodiment of asset type data 704 in accordance with theinvention, showing definitional elements for classifying five assettypes: TABLE 1 ASSET TYPE Photo Movie Audio Promo Voiceovers Metadata AdSlick Version Music On-Line edit Announcer Agency Rating Stock Airmaster# Session Date Approved Minutes Library EE Master # 1st air date ArchiveSeconds Sub Textless # Residual payment Library Art Director Date CD #Writer/ Production Producer company Black/White AKA Title CD TitleDuration Agency Box ID Type Track Title Music Telephone # Caption GenreDuration Announcer Fed ID# Character Caption Composer Cut versionsAddress Client Title Publisher Graphics Color Licensor Society Promo DubComments Release Shoot Date Material Discard Date Rating Original EPKEntry Date Foreign Code Trailer Lang. Storage Date Run Time Title KillDate Department Color/BW Duration Comments Final art Director Session DTDAT Job number Cast Composer Script Licensor Brief Publisher EDLSynopsis Off-site P Version Society Screening storage Format notesPhotographer Synopsis Rights Internet Issues rights Product ID ProductID Contract (lic.) Poster Art Version ID Internet Press Kit Contract IDInternational Version ID Run code Library Contact Project SAP NumberResolution Restrictions Shoot date Talent Title

Note that the elements defined in Table 1 are illustrative and thus areneither required nor exclusive of other elements.

Asset content 705 preferably includes one of the following: digitallyencoded asset data, a link to a file containing asset data, or areference to a location where asset data is digitally stored.Alternatively and less preferable, multiple copies of a digital assetcan be referenced or included in asset content 705.

An embodiment of DTD 700 for digital assets, which includes assetelement 701, asset metadata 703, asset type data 704, and asset content705, is shown below in Example 1 in accordance with the invention.

EXAMPLE 1

<! -DTD FOR DIGITAL ASSETS ->

<! -Digital Library Data Definition ->

<! -Supporting technologies include but not limited to XML, XSL, XSLT,XPATH, DTD Schema-> <!ELEMENT digitalAsset (assetMetadata,movieTitleMetadata?, rightsMetadata, transactionMetadata?, Photo*,Promo*, Audio*, Movie*,)> <!ELEMENT assetMetadata (#PCDATA)> <! ATTLISTassetMetadata AssetTitle CDATA #IMPLIED -this asset package has a name-AssetComments CDATA #REQUIRED -comments/description about the assetgroup- AssetVersion CDATA #REQUIRED -version, major + minor-AssetCreateDate CDATA #REQUIRED -create date- > <!ELEMENTmovieTitleMetadata (#PCDATA)> <! ATTLIST movieTitleMetadata PID CDATA#REQUIRED -product id; link to PRIME.PPROD- VID CDATA #REQUIRED-PEG--version id; LINK TO prime/pversion_general- RID CDATA #REQUIRED-rights id, for FUTURE use- Genre CDATA #REQUIRED -PEG genre, may beseveral genres [ ] FUT make multiple elements?- Rating CDATA #REQUIRED-PEG MPAA information- movieTitleLong CDATA #REQUIRED -PEG the movietitle, full name with all punctuation- movieTitleShort CDATA #REQUIRED-PEG abbreviated movie title, suitable for computer filenames; noblanks, special chars- movieTitleAKA CDATA #IMPLIED -alternate moviename; different countries- StudioProvider CDATA #IMPLIED -PEG--copyrightowner or provider of tape- Director CDATA #REQUIRED -PEG--moviedirector- Cast CDATA #REQUIRED -PEG cast members, talent [ ] FUT makemultiple elements?- SynopsisBrief CDATA #REQUIRED -PEG shortdescription- SynopsisLong CDATA #REQUIRED -full description- LanguagesCDATA #REQUIRED -PEG languages; may be several on many tracks; [ ] FUTmake multiple elements?- movieComments CDATA #REQUIRED -transmissioncommentary information- movieCreateDate CDATA #REQUIRED -PEG needs yearcreation date- movieRun_Time CDATA #REQUIRED -PEG hh:mm-movieRun_Time-Status CDATA #REQUIRED -estimated or actual-movieRunTimeMinutes CDATA #IMPLIED -RunTime minutes- movieRunTimeSecondsCDATA #IMPLIED -RunTime seconds- Run_Code CDATA #IMPLIED -(ex. 2:02 HA)-Run_Code_Type CDATA #IMPLIED -can include codes indicating type ofencoding etc.- Color/BW CDATA #IMPLIED -black & white or color- CaptionCDATA #IMPLIED -caption or description information- Keywords CDATA#IMPLIED -digital library query data for file retrieval- > <!-RightsManagement Structure-> <!ELEMENT rightsMetadata (#PCDATA)> <! ATTLISTrightsMetadata CID CDATA #REQUIRED -contract id- Amend_No CDATA #IMPLIED-contract amendment number- Ravi_ID CDATA #IMPLIED -rights availabilitywindow id- Start_Date CDATA #IMPLIED -PEG start of availability-End_Date CDATA #IMPLIED -PEG end of availability- No_of_Plays CDATA#IMPLIED -allowed number of plays per agreement- Usage_Allowed CDATA#IMPLIED -extra restrictions (ex. Rewind, pause, fast forward)- FeeCDATA #IMIPLIED -transaction fee- Authorized_Zone CDATA #IMPLIED-geography or person- World_Wide_Rights CDATA #IMPLIED -yes or no-Music_Effects CDATA #IMPLIED -yes or no (ex. train crash, explosion)-Licensor CDATA #IMPLIED -copyright holder- Coypright_Year CDATA #IMPLIED-year of copyright- > <!-Transaction Metadata Structure-> <!ELEMENTtransactionMetadata (#PCDATA)> <! ATTLIST transactionMetadata Trans_IDCDATA #REQUIRED -transaction id- Trans_Type CDATA #IMPLIED -type oftransaction- Trans_Date CDATA #IMPLIED -date of transaction-Trans_User_ID CDATA #IMPLIED -transaction author- > <!-Digital PhotoMetadata Structure-> <!ELEMENT Photo (photoMetadata,transactionMetadata)> <!ELEMENT photoMetadata (#PCDATA)> <! ATTLISTphotoMetadata <!-Baseline Information-Required fields-> BID CDATA#REQUIRED -base ID- Form_DigitalAsset CDATA #REQUIRED -photographs,graphics, location stills, or royalty fee- Orig Creation Date CDATA#REQUIRED -original creation date of digital photo asset (date field)-Resolution Type CDATA #REQUIRED <!-Production Information (extractedfrom PRIME)-> Film/Series/Program_Title CDATA #IMPLIED -program titleassociated with photograph- Orig Broadcast Date CDATA #IMPLIED -originalbroadcast date of film or series (date field extracted from PRIME)- OrigBroadcast Season CDATA #IMPLIED -original broadcast season of program orseries- Orig Release Date CDATA #IMPLIED -original release date ofprogram or series- Film/Series_Creation Date CDATA #IMPLIED -originalcreation date of film or series (date field)- Original Copyright YearCDATA #IMPLIED -copyright year (date field- Film/Series_Version CDATA#IMPLIED -version control information- Film/Series_Origin CDATA #IMPLIED-origin of film or series (e.g. HBO Theatrical)- Description_Blurb CDATA#IMPLIED -description information extracted from PRIME- Form_ProgramCDATA #IMPLIED -program type (e.g. Movie)- Genre CDATA #IMPLIED -programstyle (e.g. Romance, Drama, Comedy)- Rating CDATA #IMPLIED -programrating (e.g. R, PG)- FilmSeries_Director CDATA #IMPLIED -director offilm or series- Film/Series_Writer CDATA #IMPLIED -writer of film orseries- Film/Series-Producer CDATA #IMPLIED -producer of film or series-Film/Series_Cast Talent CDATA #IMPLIED -film or series cast and talentinformation- FilmSeries_Production CDATA #IMPLIED -production executive-Executive Film/Series Programming CDATA #IMPLIED -programming executive-Executive <!-Photograph Content Information-> Cast/Talent_Photo CDATA#IMPLIED -cast or talent that appear in photograph- Crew Name_PhotoCDATA #IMPLIED -crew that appear in photograph- Crew Position_PhotoCDATA #IMPLIED -crew position (e.g. Director, Producer, Writer)-Origin_Photo CDATA #IMPLIED -origin of photo (e.g. Warner Brothers,United Artist, Sports Illustrated)- Agency CDATA #IMPLIED -creativeagency information- Art Director_Photo CDATA #IMPLIED -Art Directorinformation- Photographer CDATA #IMPLIED -Photographer information-Requesting Department CDATA #IMPLIED -division requesting digitalcontent- Request Date CDATA #IMPLIED -date of request for digital asset(date field)- <!-Physical Photograph Information-> Orig Photo ID CDATA#IMPLIED -barcode information from photo label Orig Photo Medium CDATA#IMPLIED -(e.g. negative, print, transparency)- Orig Photo LocationCDATA #IMPLIED -location of photo in physical archive- Orig PhotoArchive Date CDATA #IMPLIED -original archive date of photo (datefield)- Orig Photo Archive Box CDATA #IMPLIED -original box number fromphysical file- Number <!-General Information-> DID CDATA #IMPLIED-digital asset id. link to Artesia UO!_ID_(—) Shoot Type CDATA #IMPLIED-type of photographic shoot (e.g. gallery, location still, acquisition)-Color CDATA #IMPLIED -color space of digital photo (e.g. black & whitecolor)- Description CDATA #IMPLIED -description of digital photographsubject matter- Comments CDATA #IMPLIED -general comments- Ready forRights CDATA #IMPLIED -yes or no- Input Date CDATA #IMPLIED -date ofingestion into Digital Library system (date field)- Input By CDATA#IMPLIED -name of person responsible for uploading asset into DigitalLibrary- Last Updated Date CDATA #IMPLIED -date of last update ormodification (date field)- Last Updated By CDATA #IMPLIED -personresponsible for last update or modification- <!-Rights Information->Asset Copyright Year CDATA #IMPLIED -digital asset year of copyright-Asset Copyright Holder CDATA #IMPLIED -digital asset copyright holder-Restrictions_Legal CDATA #IMPLIED -legal restrictions associated withdigital asset- Restrictions_Photographer CDATA #IMPLIED -photographerrestrictions associated with digital asset- Restrictions_ExclusivesCDATA #IMPLIED -yes or no- Exclusives Held Until CDATA #IMPLIED-expiration of exclusive condition linked to digital asset (date field)-Restrictions_License CDATA #IMPLIED -licensing limitations orrestrictions Limitations associated to digital asset- Legal ContactCDATA #IMPLIED -legal contact for information regarding digital contentusage- Availability End Date CDATA #IMPLIED -date when digital asset isno longer available for usage (date field)- Rights Input Date CDATA#IMPLIED -date digital rights entered into Digital Library system (datefield)- Rights Input By CDATA #IMPLIED -person entering digital rightsinfo into Digital Library system- Rights Last Updated Date CDATA#IMPLIED -date rights information was last upgraded or modified (datefield)- Rights Last Updated By CDATA #IMPLIED -person responsible forlast update or modification of rights info- <!-Digital PhotographInformation-> Filename CDATA #IMPLIED -name of digital file assigned byscanning technician (e.g. sopranos.jpg)- Format CDATA #IMPLIED -fileformat (e.g. JPEG, TIFF, PPT)- Physical Location CDATA #IMPLIED-archival location of original transparency or print- Server LocationCDATA #IMPLIED -location of digital asset storage system- DigitizingDate CDATA #IMPLIED -date digital asset was scanned (date field)-Creator CDATA #IMPLIED -name of person creating the digital file (e.g.scanning technician)- Filesize CDATA #IMPLIED -size of digital file(KB/MB)- Mode CDATA #IMPLIED -color space (e.g. RGB, CMYK, Grayscale)-Height_Inches CDATA #IMPLIED -height of digital image (inches)-Width_Inches CDATA #IMPLIED -width of digital image (inches)Height_Pixels CDATA #IMPLIED -height of digital image (pixels)- Width(Pixes10 CDATA #IMPLIED -width of digital image (pixels)- Resolution_DPICDATA #IMPLIED -digital image resolution (dots per inch) > <!-DigitalAudio Metadata Structure-> <!ELEMENT Audio (audioMetadata,transactionMetadata)> <!ELEMENT audioMetadata (#PCDATA)> <! ATTLISTaudioMetadata AID CDATA #REQUIRED -asset id- PID CDATA #REQUIRED-product ID- CID CDATA #REQUIRED -contract id- Title CDATA #IMPLIED-audio title- Music CDATA #IMPLIED -yes or no- Stock CDATA #IMPLIED -yesor no- Stock_Library CDATA #IMPLIED -music library information-Stock_Sub_Library CDATA #IMPLIED -audio library tracking information-Stock_CD_Nbr CDATA #IMPLIED -CD ID number- Stock_CD_Title CDATA #IMPLIED-CD title information- Stock_Track_Title CDATA #IMPLIED -audio trackinformation- Stock_Duration CDATA #IMPLIED -length of media section-Stock_Composer CDATA #IMPLIED -music composer information-Stock_Publisher CDATA #IMPLIED -publishing party (ex. Warner, etc.)-Stock_Society CDATA #IMPLIED -(ex. ASCAP, etc.)- Original CDATA #IMPLIED-yes or no- Original_Code CDATA #IMPLIED -x- Original_Session_Date CDATA#IMPLIED -date of recording- Original_Composer CDATA #IMPLIED -musiccomposer information- Original_Publisher CDATA #IMPLIED -party ofpublisher (ex. Warner, etc.)- Original_Society CDATA #IMPLIED -x-Rights_Issues CDATA #IMPLIED -contract information (ex. Rights,Permissions)- Contract_License CDATA #IMPLIED -yes or no- Internet CDATA#IMPLIED -yes or no- International CDATA #IMPLIED -yes or no-Library_Contact CDATA #IMPLIED -contact person- > <!-Long Form MovieMetadata Structure-> <!ELEMENT Movie (movie_FormatMetadata,TransactionMetadata)> <!ELEMENT movie_FormatMetadata (#PCDATA)> <!ATTLIST movie_FormatMetadata SAP CDATA #IMPLIED -yes or no; secondaryaudio program (ex. Spanish)- P_Version_Format CDATA #IMPLIED -refers tothe format information (PRIME Table)- Transmission_Format CDATA#REQUIRED -digital format (ex. MPEG, Quicktime, etc.)- Storage_CapacityCDATA #IMPLIED -storage requirements for digital transmission data-Unit_of_Measure_of_Capacity CDATA #IMPLIED -(ex. Megabytes MB, GigabytesGB, Terabytes TB)- Compression_Status CDATA #REQUIRED -bit rateinformation- ESP CDATA #REQUIRED -yes or no- Closed_Caption CDATA#IMPLIED -yes or no- Sound CDATA #IMPLIED -(ex. Stereo, Mono, Dolby,Dolby Digital, Dolby)- >

Example 2 below shows a sample XML document generated as part of aphotographic asset search.

EXAMPLE 2

(filename: sample.xml) <?xml version=‘1.0’ standalone=‘no’?> <DAL><Asset> <Assetmetadata PID=“200000” AssetTitle=“Chaos Factor”Comments=“Soldiers talking to man”> </Assetmetadata> <Photo><Photometadata Resolution=“72 dpi”  Talent=“Unknown”>  </Photometadata> </Photo>  <Content>chaos_1_t.jpg </Content> </Asset> <Asset><Assetmetadata PID=“141896” AssetTitle=“lf walls could talk 2”Comments=“An HBO Films trilogy examining the lesbian experience inAmerica in three different decades”> </Assetmetadata> <Photo><Photometadata Resolution=“72 dpi” Talent=“Ellen Degeneres”></Photometadata> </Photo> < Content>walls_2_t .jpg </Content> </Asset><Asset> <Assetmetadata PID=“300000” AssetTitle=“Sex and the city”Comments=“Close up portrait of Sarah JessicaParker”> </Assetmetadata><Photo> <Photometadata Resolution=“72 dpi” Talent=Sarah and cast”></Photometadata> </Photo> <Content>sex_sity_2_t.jpg </Content> </Asset><Asset> <Assetmetadata PID=“141897” AssetTitle=“If walls could talk 2”Comments=“ An HBO Films trilogy examining the lesbian experience inAmerica in three different decades”> </Assetmetadata > <Photo><Photometadata Resolution=“72 dpi” Talent=“Ellen Degeneres”></Photometadata> </Photo> < Content>walls_5_t.jpg </Content> </Asset></DAL>

XSL operates on XML search output. The output from XSL may be eitherHTML or XML both with CSS. Known software engines, such as, for example,a software engine known as XT developed by James Clark (seehttp://jclark.com/xml/xt.html for more details), can be used to convertXML into HTML. A sample command for doing such is: C:>XT sample.xmlcss.xsl output2.xml. This command generates an XML document namedoutput2.xml, which can be displayed using standard browser software.

Example 3a shows a sample XSL script. Example 3b shows a sample HTMLdocument generated by XSL on the XML search output of Example 2. Example3c shows a sample XML document with CSS also generated by XSL on the XMLsearch output of Example 2.

EXAMPLE 3a

<?xml version=“1.0”?> <xsl:stylesheet version=“1.0”xmlns:xsl=“http://www.w3.org/1999/XSL/Transform”> <xsl:templatematch=“/”> <xsl:apply-templates/> </xsl:template> </xsl:templatematch=“/DAL/Asset”> <TABLE WIDTH=“100%” BORDER=“1”><TR><TD HEIGHT=“288”><B>PID:</B><xsl:value-of select-Assetmetadata/@PID/><BR/> <B>AssetTitle: </B><xsl:value-of select=“Assetmedatada/@AssetTitle”/><BR/><B>Comments:</B><xsl:value-of select=“Assetmetadata/@Comments”/><BR/><B>Resolution:</B><xsl:value-ofselect=“Photo/Photometadata/@Resolution”/><BR/><B>Talent:</B><xsl:value-of select=“Photo/Photometadata/@Talent”/><BR/></TD><TD WIDTH=“288” HEIGHT=“288”> <xsl:apply-templates /> </TD></TR></TABLE> </xsl:template> <xsl:template match=“/DAL/Asset/Content”> <P><Ahref=”{concat(‘full_’,ancestor::Asset/Content)}“><imgsrc=“{ancestor::Asset/Content}” border=“0”/> </A></P> </xsl:template></xsl:stylesheet>

EXAMPLE 3b

<HTML> <TABLE WIDTH=“100%” BORDER=“1”><TR> <TD HEIGHT=“288”> <B>PID:</B>200000<BR/> <B>Asset Title:</B>Chaos Factor<BR/><B>Comments:</B>Soldiers talking to man<BR/> <B>Resolution:</B> 72dpi<BR/> <B>Talent:</B>Unknown<BR/> </TD><TD WIDTH=“288” HEIGHT=“288”><P><A href=“full_chaos_1_t.jpg”><img src=“chaos_1_t.jpg”border=“0”/></A></P></TD> </TR></TABLE> <TABLE WIDTH=“100%”BORDER=“1”><TR> <TD HEIGHT=“288”> <B>PID: </B>141896<BR/> <B>AssetTitle:</B>lf walls could talk 2<BR/> <B>Comments:</B>An HBO Filmstrilogy examining the lesbian experience in America in three differentdecades<BR/> <B>Resolution:</B> 72 dpi<BR/> <B>Talent:</B>EllenDegeneres<BR/></TD> <TD WIDTH=“288” HEIGHT=“288”> <P><Ahref=“full_walls_2_t.jpg”><img src=“walls_2_t.jpg” border=“0”/></A></P></TD> </TR></TABLE> <TABLE WIDTH=“100%” BORDER=“1“><TR> <TDHEIGHT=“288”><B>PID: </B>300000<BR/> <B>Asset Title:</B>Sex and thecity<BR/> <B>Comments:</B>Close up portrait of Sarah Jessica Parker<BR/><B>Resolution:</B> 72 dpi<BR/> <B>Talent:</B>Sarah and cast<BR/></TD><TD WIDTH=“288” HEIGHT=“288”> <P><A href=“full_sex_city_2_t.jpg”><imgsrc=“sex_city_2_t.jpg” border=“0” /></ A></P> </TD></TR></TABLE> <TABLEWIDTH=“100%” BORDER=“1”><TR> <TD HEIGHT=“288”> <B>PID: </B>141896<BR/><B>Asset Title:</B>If walls could talk 2<BR/> <B>Comments:</B>An HBOFilms trilogy examining the lesbian experience in America in threedifferent decades<BR/> <B>Resolution:</B> 72 dpi<BR/><B>Talent:</B>Ellen Degeneres<BR/></TD> <TD WIDTH=“288” HEIGHT=“288”><P><A href=“full_walls_5_t.jpg”> < imgsrc=“walls_5_t.jpg” border=“0”/></A></P> </TD> </TR></TABLE> </HTML>

EXAMPLE 3c

(filename: css.xml) <?xml version=1.0”?> <xsl:stylesheet version=“1.0”xmlns:xsl=“http://www .w3.org/1999/xsl/transform”> <xsl:templatematch=“/”> <xsl: processing-instructionname=“xml-stylesheet”>type=“text/css” href=“#photos” </xsl :processing-instruction> <xsl:apply-templates select=“DAL”/></xsl:template> <xsl:template match=“.”> <xsl:copy><xsl:value-ofselect=“.”/></xsl:copy> </xsl:template> <xsl:template match=“DAL ”><style id=photos”> Asset {display: block;position:relative;width:100%;height:225px;border:inset3px gray;}Assetmetadata {display:inline;font-size:14pt;} Photo{display:inline;font-size:12pt;} Photometadata{display:inline;font-size: 12pt;} Content {width:72 px;height:72px;position:relative;display:block;float:left;} <xsl:for-eachselect=“//Asset”>Content[photo<xsl:value-of select=“@PID”/> ]{background-image:url(<xsl:value-of select=“Content”/>);}</xsl:for-each> </style> <xsl:apply-templates select=“Asset”/></xsl:template> <xsl:template match=“/DAL/Asset/Content”> <Content id=“{concat(Photo’, sibling::Assetmetadata/@PID)}href=”{sibling::Asset/Content}”/> </xsl:template> <xsl:templatematch=“/DAL/Asset”> <TABLE WIDTH=“100%” BORDER=“1”><TR><TD HEIGHT=“288”><B>PID: </B><xsl:value-of select=Assetmetadata/@PID/><BR/> <B>AssetTitle:</B> <xsl:value-of select=“Assetmetadata/@AssetTitle” /><BR/><B>Comments:</B><xsl:value-of select=“Assetmetadata/@Comments” /><BR/><B>Resolution:</B><xsl:value-ofselect=”Photo/Photometadata/@Resolution”/><BR/><B>Talent:</B><xsl:value-of select=“Photo/Photometadatal@Talent”/>< BR/></TD> <TD WIDTH=“288” HEIGHT=“288”> <xsl:apply-templates /> </TD></TR></TABLE> </xsl:template> <xsl:template match=“/DAL Asset/Content”><P><A href=“{concat(‘photo’,sibling::asset/content )}”> <imgsrc=“{ancestor::Asset/Content}” border=“0”/> </A></P> </xsl:template></xsl:stylesheet>

Thus it is seen that XML data definitions for digital assets areprovided that can be used as a standardized dictionary for applicationand platform independent exchange and repurposing of those assets. Oneskilled in the art will appreciate that the present invention can bepracticed by other than the described embodiments, which are presentedfor purposes of illustration and not of limitation, and the presentinvention is limited only by the claims which follow.

1. A method of storing digital assets, the digital assets comprising atleast three different types of digital assets selected from the groupconsisting of still images, video recordings, movies, audio recordings,graphics, promos, voiceovers, and text, the method comprising: arrangingmetadata of a first type of digital asset in accordance with a documenttype definition (DTD) comprising declared elements and attributes for atleast three different types of digital assets, at least a first typeselected from the group consisting of video recordings and audiorecordings and at least one other type selected from the groupconsisting of still images, movies, graphics, promos, voiceovers, andtext; arranging metadata of a second type of digital asset in accordancewith the DTD, the second type different from the first type; arrangingmetadata of a third type of digital asset in accordance with the DTD,the third type different from the first type and the second type;storing a first digital asset of the first type in a database; storing asecond digital asset of the second type in the same database as thefirst digital asset; and storing a third digital asset of the third typein the same database as the first and second digital assets.
 2. Themethod of claim 1 further comprising storing the metadata of the first,second, and third types of digital assets in the same database as thefirst, second, and third digital assets.
 3. The method of claim 1wherein the arranging of metadata for a first type of digital assetcomprises arranging metadata of a first type of digital asset inaccordance with a DTD comprising declared elements and attributes forphotographs wherein the photograph metadata attributes comprise at leastone of: a definition for black/white; a definition for color; adefinition for caption; and a definition for legal restrictionsassociated with a photograph.
 4. The method of claim 1 wherein thearranging of metadata for a first type of digital asset comprisesarranging metadata of a first type of digital asset in accordance with aDTD comprising declared elements and attributes for audio recordingswherein the audio metadata attributes comprise at least one of: adefinition for music; a definition for track title; a definition forduration; a definition for compact disc (CD) number; a definition for CDtitle; and a definition for rights issues regarding use of an audiorecording.
 5. The method of claim 1 wherein the arranging of metadatafor a first type of digital asset comprises arranging metadata of afirst type of digital asset in accordance with a DTD comprising declaredelements and attributes for movies wherein the movie metadata attributescomprise at least one of: a definition for title; a definition forversion; a definition for rating; a definition for minutes; a definitionfor release date; a definition for run time; a definition for color; adefinition for synopsis; a definition for director; a definition forcast; and a definition for allowable usage of a movie.
 6. The method ofclaim 1 wherein the arranging of metadata for a first type of digitalasset comprises arranging metadata of a first type of digital asset inaccordance with a DTD comprising declared elements and attributes forvideo recordings wherein the video-recordings-metadata attributescomprise a definition for rights issues regarding use of a videorecording.
 7. The method of claim 6 wherein the definition for rightsissues comprises at least one of: a contract identifier; an availabilitystart date; an availability end date; an allowed number of plays peragreement; a copyright holder identifier; and a worldwide rightsidentifier.
 8. A method of retrieving digital assets from a digitalasset library, the digital assets comprising at least three differenttypes of digital assets selected from the group consisting of stillimages, video recordings, movies, audio recordings, graphics, promos,voiceovers, and text, the method comprising: receiving a request for atleast one digital asset, the request comprising criteria to which therequested digital asset is to conform; accessing a document typedefinition (DTD) of digital assets stored in the digital asset library,the DTD comprising declared elements and attributes for at least threedifferent types of digital assets, at least a first type selected fromthe group consisting of video recordings and audio recordings and atleast one other type selected from the group consisting of still images,movies, graphics, promos, voiceovers, and text, the DTD furthercomprising declared elements and attributes for rights management of atleast three different types of digital assets selected from the groupconsisting of still images, video recordings, movies, graphics, promos,and voiceovers; searching a database of the digital asset library forthe requested digital asset, the database comprising a plurality ofrecords identifying digital assets of at least three different typesselected from the group consisting of still images, video recordings,movies, audio recordings, graphics, promos, voiceovers, and text; andreturning a list of at least two digital assets in response to the twodigital assets each conforming to the criteria, the two digital assetseach being of a different asset type selected from the group consistingof still images, video recordings, movies, audio recordings, graphics,promos, voiceovers, and text.
 9. The method of claim 8 wherein thecriteria comprises a keyword.
 10. The method of claim 8 wherein thecriteria comprises a product ID and a version ID.
 11. The method ofclaim 8 further comprising: receiving a request for a copy of one of thetwo digital assets conforming to the criteria; accessing the one of thetwo digital assets stored in a computer storage device of the digitalasset library; and creating a copy of the one of the two digital assetsin compliance with the request for a copy.
 12. The method of claim 8wherein the DTD is encoded in extensible markup language (XML).
 13. Themethod of claim 8 wherein the plurality of database records correspondsto the DTD.
 14. The method of claim 8 wherein the DTD comprises declaredelements and attributes for rights management of at least two differenttypes of digital assets selected from the group consisting of videorecordings, movies, audio recordings, graphics, and text.
 15. The methodof claim 8 wherein the DTD comprises declared elements and attributesfor still images, video recordings, and audio recordings.
 16. The methodof claim 8 wherein the DTD comprises declared elements and attributesfor movies, graphics, and voiceovers.
 17. A method of retrieving digitalassets stored in a single database, the digital assets comprising atleast three different types of digital assets selected from the groupconsisting of still images, video recordings, movies, audio recordings,graphics, promos, voiceovers, and text, the method comprising: receivinga request for at least one digital asset, the request comprisingcriteria to which the requested digital asset is to conform; accessing adocument type definition (DTD) comprising declared elements andattributes for all the types of digital assets stored in the singledatabase, the DTD comprising declared elements and attributes for afirst type of asset selected from the group consisting of videorecordings and audio recordings and at least one other type selectedfrom the group consisting of still images, movies, graphics, promos,voiceovers, and text, the DTD further comprising declared elements andattributes for rights management of at least three different types ofdigital assets selected from the group consisting of still images, videorecordings, movies, graphics, promos, and voiceovers; searching thedatabase for the requested digital asset, the database comprising aplurality of records identifying digital assets of at least threedifferent types selected from the group consisting of still images,video recordings, movies, audio recordings, graphics, promos,voiceovers, and text; and returning a list of at least two digitalassets in response to the two digital assets each conforming to thecriteria, the two digital assets each being of a different asset typeselected from the group consisting of still images, video recordings,movies, audio recordings, graphics, promos, voiceovers, and text. 18.The method of claim 17 wherein the criteria comprises a keyword.
 19. Themethod of claim 17 wherein the criteria comprises a product ID and aversion ID.
 20. The method of claim 17 wherein the criteria comprises aname of an actor.